Method and apparatus for modifying compressed files

ABSTRACT

A method, apparatus and computer program product are provided for preparing and installing update packages for compressed files. In the context of a method, a method for preparing an update package is provided that includes receiving an original file and a modified file, causing the original file and the modified file to be decompressed, and generating one or more delta files based on the decompressed original file and the decompressed modified file. A corresponding method for installing an update package is also provided that includes receiving the update package comprising one or more delta files corresponding to an original file, causing the original file to be decompressed, generating one or more modified subfiles based on the one or more delta files and the decompressed original file, and generating a compressed modified file by compressing the one or more modified subfiles.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/542,093, filed Jul. 5, 2012, the entire contents of which areincorporated herein by reference.

TECHNOLOGICAL FIELD

An example embodiment of the present invention relates generally totechniques for modifying compressed files and, more particularly, to amethod and apparatus for preparing and installing update packages forcompressed files.

BACKGROUND

The software of certain user devices occasionally may need to be updatedon occasion by the device manufacturer, a service provider, a softwarevendor, or another party. These updates may be provided in many ways.For example, if the user device is a wireless device, such as acellphone, personal digital assistant (PDA), tablet, or the like, thatcommunicates wirelessly with a network, an update package may beprovided over the air, i.e., provided via a wireless local area network(WLAN), cell network, or other such wireless communication network, andinstalled on the device. In such a case, and indeed even in the case ofa wired device, it is desirable that the update package be as small aspossible to avoid download costs for the user and network traffic forthe network operator.

One method of keeping the size of an update package relatively small isthe use of a “delta file,” which contains only the difference between anold file and a new file. Thus, the user only needs to download a deltafile instead of the entire modified file. The device may then use thedelta file to modify the old file so that it is identical to the newfile.

While the use of delta files is generally an efficient means ofproviding update packages, problems can be introduced when using themwith compressed files. In particular, compression may introduce bitchanges which cause the differences between a compressed original fileand a compressed modified file to accumulate to the point that aresulting delta file may be almost as large as the entire modified file.

BRIEF SUMMARY

A method, apparatus and computer program product are therefore providedaccording to an example embodiment of the present invention formodifying compressed files. In this regard, the method, apparatus, andcomputer program product of one embodiment may efficiently preparebinary update packages for compressed files. The method, apparatus, andcomputer program of another embodiment may install theefficiently-prepared binary update package for compressed files. Thus,by utilizing the method, apparatus, and computer program of theseembodiments, the amount of data that may be exchanged between a devicereceiving an update and the provider of the update may be reduced.

In one embodiment, a method is provided that includes receiving anoriginal file and a modified file. The method further includes causingthe original file and the modified file to be decompressed andgenerating one or more delta files based on the decompressed originalfile and the decompressed modified file.

In another embodiment, a method is provided that includes receiving anupdate package comprising one or more delta files corresponding to anoriginal file. The method further includes causing the original file tobe decompressed, generating one or more modified subfiles based on theone or more delta files and the decompressed original file, andgenerating a compressed modified file by compressing the one or moremodified subfiles.

In a further embodiment, an apparatus is provided that includes at leastone processor and at least one memory including program codeinstructions, the at least one memory and the program code instructionsbeing configured to, with the processor, direct the apparatus to atleast receive an original file and a modified file. The apparatus isfurther caused to cause the original file and the modified file to bedecompressed and generate one or more delta files based on thedecompressed original file and the decompressed modified file.

In another embodiment, an apparatus is provided that includes at leastone processor and at least one memory including program codeinstructions, the at least one memory and the program code instructionsbeing configured to, with the processor, direct the apparatus to atleast receive an update package comprising one or more delta filescorresponding to an original file. The apparatus is further caused tocause the original file to be decompressed, generate one or moremodified subfiles based on the one or more delta files and thedecompressed original file, and to generate a compressed modified fileby compressing the one or more modified subfiles.

In an even further embodiment, a computer program product is providedthat includes a non-transitory computer readable medium storing programcode portions therein. The computer program code instructions areconfigured to, upon execution, cause an apparatus to at least receive anoriginal file and a modified file. The computer program codeinstructions are configured to, upon execution, cause the apparatus toat least cause the original file and the modified file to bedecompressed and generate one or more delta files based on thedecompressed original file and the decompressed modified file.

In another embodiment, a computer program product is provided thatincludes a non-transitory computer readable medium storing program codeportions therein. The computer program code instructions are configuredto, upon execution, cause an apparatus to at least receive an updatepackage comprising one or more delta files corresponding to an originalfile. The computer program code instructions are configured to, uponexecution, cause the apparatus to at least cause the original file to bedecompressed, generate one or more modified subfiles based on the one ormore delta files and the decompressed original file, and to generate acompressed modified file by compressing the one or more modifiedsubfiles.

In a still further embodiment, an apparatus is provided that includesmeans for receiving an original file and a modified file. The apparatusfurther includes means for causing the original file and the modifiedfile to be decompressed and means for generating one or more delta filesbased on the decompressed original file and the decompressed modifiedfile.

In another embodiment, an apparatus is provided that includes means forreceiving an update package comprising one or more delta filescorresponding to an original file. The apparatus further includes meansfor causing the original file to be decompressed, means for generatingone or more modified subfiles based on the one or more delta files andthe decompressed original file, and means for generating a compressedmodified file by compressing the one or more modified subfiles.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described example embodiments of the invention in generalterms, reference will now be made to the accompanying drawings, whichare not necessarily drawn to scale, and wherein:

FIG. 1 is a schematic representation of a system that may supportexample embodiments of the present invention;

FIG. 2 is a block diagram of an electronic device that may be configuredto implement example embodiments of the present invention;

FIG. 3 is a block diagram of an apparatus that may be embodied by orassociated with an electronic device, and may be configured to implementexample embodiments of the present invention;

FIGS. 4a and 4b are flowcharts illustrating update package preparationand installation procedures for uncompressed files;

FIGS. 5a and 5b are flowcharts illustrating update package preparationand installation procedures for compressed files according to exampleembodiments of the present invention; and

FIGS. 6 and 7 are flowcharts illustrating operations according toembodiments of the present invention.

DETAILED DESCRIPTION

Some embodiments of the present invention will now be described morefully hereinafter with reference to the accompanying drawings, in whichsome, but not all, embodiments of the invention are shown. Indeed,various embodiments of the invention may be embodied in many differentforms and should not be construed as limited to the embodiments setforth herein; rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. Like referencenumerals refer to like elements throughout. As used herein, the terms“data,” “content,” “information,” and similar terms may be usedinterchangeably to refer to data capable of being transmitted, received,processed and/or stored in accordance with embodiments of the presentinvention. Also as used herein, the terms “modify” and “update” may beused interchangeably to refer to modifying or changing a file inaccordance with embodiments of the present invention, and may refer tothe file being “updated” to match a more current version, modified tomatch an older version, or modified in any other way or for any otherpurpose. Moreover, a “file” as used herein may refer to any collectionof related data or program records stored as a unit. Thus, a “file” asused herein may, for example, represent any discrete component of asoftware program, firmware, or any other set of machine or computerreadable instructions or data. Thus, use of any such terms should not betaken to limit the spirit and scope of embodiments of the presentinvention.

Additionally, as used herein, the term ‘circuitry’ refers to (a)hardware-only circuit implementations (e.g., implementations in analogcircuitry and/or digital circuitry); (b) combinations of circuits andcomputer program product(s) comprising software and/or firmwareinstructions stored on one or more computer readable memories that worktogether to cause an apparatus to perform one or more functionsdescribed herein; and (c) circuits, such as, for example, amicroprocessor(s) or a portion of a microprocessor(s), that requiresoftware or firmware for operation even if the software or firmware isnot physically present. This definition of ‘circuitry’ applies to alluses of this term herein, including in any claims. As a further example,as used herein, the term ‘circuitry’ also includes an implementationcomprising one or more processors and/or portion(s) thereof andaccompanying software and/or firmware. As another example, the term‘circuitry’ as used herein also includes, for example, a basebandintegrated circuit or applications processor integrated circuit for amobile phone or a similar integrated circuit in a server, a cellularnetwork device, other network device, and/or other computing device.

As defined herein, a “computer-readable storage medium,” which refers toa physical storage medium (e.g., volatile or non-volatile memorydevice), can be differentiated from a “computer-readable transmissionmedium,” which refers to an electromagnetic signal.

As described below, a method, apparatus and computer program product areprovided for modifying, e.g., updating, compressed files. In thisregard, the method, apparatus and computer program product of an exampleembodiment may efficiently prepare binary update packages for compressedfiles. The method, apparatus, and computer program of another embodimentmay install the efficiently-prepared binary update package. Thus, themethod, apparatus, and computer program of these embodiments may allowthe amount of data that may be exchanged between a device receiving anupdate package containing updates for compressed files and the providerof the update package to be reduced.

FIG. 1 illustrates a block diagram of a system that may benefit fromembodiments of the present invention. While FIG. 1 illustrates oneexample of a system that would benefit from the present invention,numerous other systems and configurations may also benefit fromembodiments of the present invention. With reference to FIG. 1, however,the system may include a user device 11, connected to a network 14 viaan access point 10, and a network entity 13, such as a server alsoconnected to network 14. User device 11 may be any device that isconfigured to communicate over any type of network. For example, userdevice 11 may be a mobile terminal, such as a mobile telephone, PDA,pager, laptop computer, tablet computer, or any of numerous other handheld or portable communication devices, computation devices, contentgeneration devices, content consumption devices, or combinations. Userdevice 11 and network entity 13 may include or be associated with anapparatus 45, such as shown in FIG. 3, configured in accordance withembodiments of the present invention, as described below.

As shown in FIG. 1, user device 11 and network entity 13 may communicatewith one another via network 14, which user device 11 may connect to viaaccess point 10. User device 11 and access point 10 may communicate witheach other via wireless means such as, for example, WI-FI, BLUETOOTH, orthe like, or via wired means such as Ethernet, USB (Universal SerialBus), or the like. Access point 10 may also allow device 11 to accessnetwork 14 via a wireless network, such as a Long Term Evolution (LTE)network, an LTE-Advanced (LTE-A) network, a Global Systems for Mobilecommunications (GSM) network, a Code Division Multiple Access (CDMA)network, e.g., a Wideband CDMA (WCDMA) network, a CDMA2000 network orthe like, a General Packet Radio Service (GPRS) network or other type ofnetwork. Access point 10 may communicate with network 14 via wiredmeans, such as via fiber optic or coaxial cable, twisted-pair Ethernetcable, digital subscriber line (DSL), or by connecting with a wirelessnetwork, such as a Long Term Evolution (LTE) network, an LTE-Advanced(LTE-A) network, a Global Systems for Mobile communications (GSM)network, a Code Division Multiple Access (CDMA) network, e.g., aWideband CDMA (WCDMA) network, a CDMA2000 network or the like, a GeneralPacket Radio Service (GPRS) network or other type of network. Networkentity 13 may similarly communicate with network 14 via wired orwireless means. Thus, it should be understood that embodiments of thepresent invention may be implemented in any type of system in which adevice, such as device 11, may communicate with an update provider, suchas network entity 13. The means by which the device and update providercommunicate, and any intervening entities, devices, networks,communications means, or the like, are not material to the operations ofembodiments of the present invention.

In one embodiment, user device 11 may be embodied by a mobile terminal.In this regard, a block diagram of a mobile terminal 25 that wouldbenefit from embodiments of the present invention is illustrated in FIG.2. It should be understood, however, that the mobile terminal 25 asillustrated and hereinafter described is merely illustrative of one typeof user device that may benefit from embodiments of the presentinvention and, therefore, should not be taken to limit the scope ofembodiments of the present invention. As such, although numerous typesof mobile terminals, such as PDAs, mobile telephones, pagers, mobiletelevisions, gaming devices, laptop computers, cameras, tabletcomputers, touch surfaces, wearable devices, video recorders,audio/video players, radios, electronic books, positioning devices(e.g., global positioning system (GPS) devices), or any combination ofthe aforementioned, may readily employ embodiments of the presentinvention, other user devices including fixed (non-mobile) electronicdevices may also employ some example embodiments.

The mobile terminal 25 may include an antenna 17 (or multiple antennas)in operable communication with a transmitter 18 and a receiver 20. Themobile terminal 25 may further include an apparatus, such as a processor22 or other processing device (e.g., processor 50 of the apparatus ofFIG. 3), which controls the provision of signals to and the receipt ofsignals from the transmitter 18 and receiver 20, respectively. Thesignals may include signaling information in accordance with the airinterface standard of the applicable cellular system, and also userspeech, received data and/or user generated data. In this regard, themobile terminal 25 is capable of operating with one or more airinterface standards, communication protocols, modulation types, andaccess types. By way of illustration, the mobile terminal 25 is capableof operating in accordance with wireless communication mechanisms. Forexample, mobile terminal 25 may be capable of communicating in awireless local area network (WLAN) or other communication networks, forexample in accordance with one or more of the IEEE 802.11 family ofstandards, such as 802.11a, b, g, or n. As an alternative (oradditionally), the mobile terminal 25 may be capable of operating inaccordance with any of a number of first, second, third and/orfourth-generation cellular communication protocols or the like. Forexample, the mobile terminal 25 may be capable of operating inaccordance with second-generation (2G) wireless communication protocolsIS-136 (time division multiple access (TDMA)), GSM (global system formobile communication), and IS-95 (code division multiple access (CDMA)),or with third-generation (3G) wireless communication protocols, such asUniversal Mobile Telecommunications System (UMTS), CDMA2000, widebandCDMA (WCDMA) and time division-synchronous CDMA (TD-SCDMA), with 3.9Gwireless communication protocol such as evolved UMTS Terrestrial RadioAccess Network (E-UTRAN), with fourth-generation (4G) wirelesscommunication protocols (e.g., Long Term Evolution (LTE) or LTE-Advanced(LTE-A) or the like.

In some embodiments, the processor 22 may include circuitry desirablefor implementing audio and logic functions of the mobile terminal 25.For example, the processor 22 may be comprised of a digital signalprocessor device, a microprocessor device, and various analog to digitalconverters, digital to analog converters, and other support circuits.Control and signal processing functions of the mobile terminal 25 areallocated between these devices according to their respectivecapabilities. The processor 22 thus may also include the functionalityto convolutionally encode and interleave message and data prior tomodulation and transmission. The processor 22 may additionally includean internal voice coder, and may include an internal data modem.Further, the processor 22 may include functionality to operate one ormore software programs, which may be stored in memory. For example, theprocessor 22 may be capable of operating a connectivity program, such asa conventional Web browser. The connectivity program may then allow themobile terminal 25 to transmit and receive Web content, such aslocation-based content and/or other web page content, according to aWireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP)and/or the like, for example.

The mobile terminal 25 may also comprise a user interface including anoutput device such as a conventional earphone or speaker 26, a ringer24, a microphone 28, a display 30, and a user input interface, all ofwhich are coupled to the processor 22. The user input interface, whichallows the mobile terminal 25 to receive data, may include any of anumber of devices allowing the mobile terminal 25 to receive data, suchas a keypad 32, a touch screen display (display 30 providing an exampleof such a touch screen display) or other input device. In embodimentsincluding the keypad 32, the keypad 32 may include the conventionalnumeric (0-9) and related keys (#, *), and other hard and soft keys usedfor operating the mobile terminal 25. Alternatively or additionally, thekeypad 32 may include a conventional QWERTY keypad arrangement. Thekeypad 32 may also include various soft keys with associated functions.In addition, or alternatively, the mobile terminal 25 may include aninterface device such as a joystick or other user input interface. Someembodiments employing a touch screen display, as described furtherbelow, may omit the keypad 32 and any or all of the speaker 26, ringer24, and microphone 28 entirely. The mobile terminal 25 further includesa battery, such as a vibrating battery pack, for powering variouscircuits that are required to operate the mobile terminal 25, as well asoptionally providing mechanical vibration as a detectable output.

The mobile terminal 25 may further include a user identity module (UIM)34. The UIM 34 is typically a memory device having a processor built in.The UIM 34 may include, for example, a subscriber identity module (SIM),a universal integrated circuit card (UICC), a universal subscriberidentity module (USIM), a removable user identity module (R-UIM), etc.The UIM 34 typically stores information elements related to a mobilesubscriber. In addition to the UIM 34, the mobile terminal 25 may beequipped with memory. For example, the mobile terminal 25 may includevolatile memory 36, such as volatile Random Access Memory (RAM)including a cache area for the temporary storage of data. The mobileterminal 15 may also include other non-volatile memory 38, which may beembedded and/or may be removable. The memories may store any of a numberof pieces of information, and data, used by the mobile terminal 15 toimplement the functions of the mobile terminal 25.

Example embodiments of the invention will now be described withreference to FIG. 3, in which certain elements of an apparatus 45 forpreparing and installing update packages for compressed files aredepicted. In order to prepare an update package, the apparatus 45 ofFIG. 3 may be employed, for example, in conjunction with network entity13. In order to install an update package, the apparatus 45 of FIG. 3may be employed, for example, in conjunction with user device 11.However, it should be noted that the apparatus 45 of FIG. 3 may also beemployed in connection with a variety of other devices, both mobile andfixed, in order to prepare or install update packages. For example, theapparatus 45 may be embodied by or associated with a personal computeror other user terminal.

It should also be noted that while FIG. 3 illustrates one example of aconfiguration of an apparatus 45 for preparing and/or installing updatepackages, numerous other configurations may also be used to implementembodiments of the present invention. As such, in some embodiments,although devices or elements are shown as being in communication witheach other, hereinafter such devices or elements should be considered tobe capable of being embodied within a same device or element and thus,devices or elements shown in communication should be understood toalternatively be portions of the same device or element.

Referring now to FIG. 3, the apparatus 45 for preparing and/orinstalling update packages for compressed files may include or otherwisebe in communication with a processor 50, a communication interface 54,and a memory device 56. As described below and as indicated by thedashed lines in FIG. 3, the apparatus 45 may also optionally include auser interface 52 in some embodiments, such as embodiments in which theapparatus 45 is embodied as user device 11. In some embodiments, theprocessor 50 (and/or co-processors or any other processing circuitryassisting or otherwise associated with the processor 50) may be incommunication with the memory device 56 via a bus for passinginformation among components of the apparatus 45. The memory device 56may include, for example, one or more volatile and/or non-volatilememories. In other words, for example, the memory device 56 may be anelectronic storage device (e.g., a computer readable storage medium)comprising gates configured to store data (e.g., bits) that may beretrievable by a machine (e.g., a computing device like the processor50). In the embodiment in which the apparatus 45 is embodied as a mobileterminal 25, the memory device 56 may be embodied by the memory 36, 38.The memory device 56 may be configured to store information, data,content, applications, instructions, or the like, for enabling theapparatus to carry out various functions in accordance with an exampleembodiment of the present invention. For example, the memory device 56could be configured to buffer input data for processing by the processor50. Additionally or alternatively, the memory device 56 could beconfigured to store instructions for execution by the processor 50.

The apparatus 45 may, in some embodiments, be embodied by or associatedwith a user terminal (e.g., mobile terminal 25) or a fixed communicationdevice or computing device (e.g., network entity 13) configured toemploy an example embodiment of the present invention. However, in someembodiments, the apparatus 45 may be embodied as a chip or chip set. Inother words, the apparatus 45 may comprise one or more physical packages(e.g., chips) including materials, components and/or wires on astructural assembly (e.g., a baseboard). The structural assembly mayprovide physical strength, conservation of size, and/or limitation ofelectrical interaction for component circuitry included thereon. Theapparatus 45 may therefore, in some cases, be configured to implement anembodiment of the present invention on a single chip or as a single“system on a chip.” As such, in some cases, a chip or chipset mayconstitute means for performing one or more operations for providing thefunctionalities described herein.

The processor 50 may be embodied in a number of different ways. Forexample, the processor 50 may be embodied as one or more of varioushardware processing means such as a coprocessor, a microprocessor, acontroller, a digital signal processor (DSP), a processing element withor without an accompanying DSP, or various other processing circuitryincluding integrated circuits such as, for example, an ASIC (applicationspecific integrated circuit), an FPGA (field programmable gate array), amicrocontroller unit (MCU), a hardware accelerator, a special-purposecomputer chip, or the like. As such, in some embodiments, the processor50 may include one or more processing cores configured to performindependently. A multi-core processor may enable multiprocessing withina single physical package. Additionally or alternatively, the processor50 may include one or more processors configured in tandem via the busto enable independent execution of instructions, pipelining and/ormultithreading. In the embodiment in which the apparatus 45 is embodiedas a mobile terminal 25, the processor 50 may be embodied by theprocessor 22.

In an example embodiment, the processor 50 may be configured to executeinstructions stored in the memory device 56 or otherwise accessible tothe processor 50. Alternatively or additionally, the processor 50 may beconfigured to execute hard coded functionality. As such, whetherconfigured by hardware or software methods, or by a combination thereof,the processor 50 may represent an entity (e.g., physically embodied incircuitry) capable of performing operations according to an embodimentof the present invention while configured accordingly. Thus, forexample, when the processor 50 is embodied as an ASIC, FPGA or the like,the processor 50 may be specifically configured hardware for conductingthe operations described herein. Alternatively, as another example, whenthe processor 50 is embodied as an executor of software instructions,the instructions may specifically configure the processor 50 to performthe algorithms and/or operations described herein when the instructionsare executed. However, in some cases, the processor 50 may be aprocessor of a specific device (e.g., a mobile terminal or networkentity) configured to employ an embodiment of the present invention byfurther configuration of the processor 50 by instructions for performingthe algorithms and/or operations described herein. The processor 50 mayinclude, among other things, a clock, an arithmetic logic unit (ALU) andlogic gates configured to support operation of the processor 50.

Meanwhile, the communication interface 54 may be any means such as adevice or circuitry embodied in either hardware or a combination ofhardware and software that is configured to receive and/or transmit datafrom/to a network, such as network 14, and/or any other device or modulein communication with the apparatus 45. In this regard, thecommunication interface 54 may include, for example, an antenna (ormultiple antennas) and supporting hardware and/or software for enablingcommunications with a wireless communication network. Additionally oralternatively, the communication interface 54 may include the circuitryfor interacting with the antenna(s) to cause transmission of signals viathe antenna(s) or to handle receipt of signals received via theantenna(s). In some environments, the communication interface 54 mayalternatively or also support wired communication. As such, for example,the communication interface 54 may include a communication modem and/orother hardware/software for supporting communication via cable, digitalsubscriber line (DSL), universal serial bus (USB) or other mechanisms.In the embodiment in which the apparatus 45 is embodied as a mobileterminal 15, the communication interface 54 may be embodied by theantenna 16, transmitter 18, receiver 20 or the like.

In some embodiments, such as instances in which the apparatus 45 isembodied by user device 11, the apparatus 45 may include a userinterface 52 that may, in turn, be in communication with the processor50 to receive an indication of a user input and/or to cause provision ofan audible, visual, mechanical or other output to the user. As such, theuser interface 52 may include, for example, a keyboard, a mouse, ajoystick, a display, a touch screen(s), touch areas, soft keys, amicrophone, a speaker, or other input/output mechanisms. Alternativelyor additionally, the processor 50 may comprise user interface circuitryconfigured to control at least some functions of one or more userinterface elements such as, for example, a speaker, ringer, microphone,display, and/or the like. The processor 50 and/or user interfacecircuitry comprising the processor 50 may be configured to control oneor more functions of one or more user interface elements throughcomputer program instructions (e.g., software and/or firmware) stored ona memory accessible to the processor 50 (e.g., memory device 56, and/orthe like). In other embodiments, however, such as in instances in whichthe apparatus 45 is embodied by network entity 13, the apparatus 45 maynot include a user interface 52.

Before proceeding with the description of various embodiments of thepresent invention, it is beneficial to consider the operations anddisadvantages of applying an update package preparation and installationprocedure, as depicted in FIGS. 4a and 4b , to compressed files. In anupdate package preparation procedure, as depicted in FIG. 4a , anoriginal file 400 and a modified, e.g., updated, file 401 are fed to adelta generator 410. The delta generator 410 compares the original 400and modified 401 files and generates a delta file 450 based on thedifferences. This delta file 450 is then provided to a device forinstallation. The installation procedure, as depicted in FIG. 4b ,involves feeding the original file 400 and delta file 450 into a deltainstaller 420. The delta installer applies the changes represented inthe delta file 450 to the original file 400, thus generating a modifiedfile 401 identical to the modified file 401 used to create the deltafile 450. The advantage of this type of procedure for updating files isthat a delta file 450, which contains only differences between originalfile 400 and modified file 401, will likely be significantly smaller,and thus easier to transmit, than modified file 401.

However, as alluded to in the Background section, when the original file400 and modified file 401 are compressed files, the efficiency of theabove described procedures may be lost. As used herein, a “compressedfile” may refer to any file that contains one or more subfiles that havebeen compressed according to any compression algorithm, such that thesize of the compressed file is, preferably, no more than the sum of thesizes of the subfile(s) it contains. The compression algorithm may, forexample, be a lossless compression algorithm such as, for example, gzip,lzma, png or the like. The compression algorithm may also be a “lossy”compression algorithm such as, for example, jpeg, mp3, or the like.Accordingly, an “uncompressed file” or “decompressed file” may refer tothe one or more subfiles previously contained in the correspondingcompressed file. The algorithm used to create a compressed file may makeany number of changes to the subfile(s) in order to reduce their size.Thus, consider hypothetical files A and B, which contain program codeand differ only in that file B contains one additional function that Adoes not contain. Because the difference between these files is small, adelta file generated based on files A and B will likely also be small.However, compressed file A will likely be quite different, especially ata binary level, from uncompressed file A, and likely even more differentfrom compressed file B. Thus, a delta file generated based on compressedfile A and compressed file B may be quite large, and in some cases,almost as large as compressed file B itself. For this reason, the deltafile-based update package preparation/installation procedure depicted inFIGS. 4a and 4b may be ill-suited for use with compressed files.

Thus, referring now to FIG. 5a , an overview of the data flows for theprocess of preparing an update package for updating one or morecompressed files according to an embodiment of the present invention isdepicted. A representation of the corresponding process of installing anupdate package that updates one or more compressed files is presented inFIG. 5 b. Referring now to FIG. 5a , a compressed original file 500 anda compressed modified file 501 are first decompressed via ade-compressor 530. Next, the decompressed original file, e.g., the oneor more original subfiles, and decompressed modified file, e.g., the oneor more modified subfiles, are fed to delta generator 510, whichgenerates one or more delta files 550 based on the uncompressed original500 and modified 501 files, e.g., by comparing each of the one or moreoriginal subfiles to its corresponding modified subfile. Referring nowto FIG. 5b , the installation procedure begins with compressed originalfile 500 being decompressed by de-compressor 530. The uncompressedoriginal file(s) and the delta file(s) 550 are then fed into deltainstaller 520, which updates the uncompressed original file, e.g., theoriginal subfiles, according to the one or more delta files 550, e.g.,by modifying each original subfile according to its corresponding deltafile. The resulting decompressed modified file, e.g., one or moremodified subfiles, is then fed into compressor 540, resulting incompressed modified file 501. It should be understood that compressor540, de-compressor 530, delta generator 510, and delta installer 520 maybe embodied as hardware or software modules. That is, each may beembodied, for example, as circuitry, or be implemented as programinstructions stored in memory and executed by a processor, such asmemory 56 and processor 50 of apparatus 45.

Thus, turning now to FIG. 6, the operations of apparatus 45 forpreparing an update package will now be described in more detail,including examples of operations that may precede or follow thosedepicted in FIG. 5a . In this regard and as described below, theoperations of FIG. 6 may be performed by an apparatus 45, such as shownin FIG. 3, embodied by or otherwise associated with network entity 13.In this regard, the apparatus 45 may include means, such as processor50, memory device 56, and communication interface 54 or the like, forreceiving an original file and a modified file. See operation 600. Theoriginal and modified files may be already stored in memory, such asmemory 56, or may, for example, be provided to the apparatus 45 by anetwork operator, software vendor, hardware manufacturer, or any otherparty, such as via network 14. Apparatus 45 may further include means,such as those mentioned above, for determining whether the original andmodified files are compressed files. See operation 610. According to anexample embodiment, apparatus 45 may, for example, determine whether thefiles are compressed files as part of determining the file types of themodified and original files, such as whether the file is a compressedfile, a folder, a symbolic link, a normal file, or any other type offile. As the modified and original files may be the same type, apparatus45 may, according to an example embodiment, only determine a type forone of the files, such as by only determining the type of the originalfile or the modified file. Whether apparatus 45 determines the types ofboth the modified and original files, or only one file of the pair, ormerely whether each pair or individual file is compressed, apparatus 45may further cause these results to be stored, such as in a configurationfile.

Having determined whether the files are compressed, apparatus 45 mayfurther include means, such as processor 50 and memory device 56 or thelike, for generating one or more delta files. Thus, apparatus 45 mayinclude means, such as those just mentioned, for generating a delta filebased on the original and modified files in the manner depicted in FIG.4a and discussed above in an instance in which the original and modifiedfiles are not compressed files. See operation 611. Apparatus 45 may alsoinclude means, such as those mentioned above, for generating a deltafile based on the original and modified files in the manner depicted inFIG. 5a in an instance in which the original and modified files arecompressed files. Thus, apparatus 45 may include means for decompressingboth the compressed original file and the compressed modified file. Seeoperation 620. Apparatus 45 may further include means for generating oneor more delta files based on the decompressed original file anddecompressed modified file. See operation 630.

Having generated the one or more delta files, apparatus 45 may furtherinclude means, such as processor 50, memory device 56, and communicationinterface 54 or the like, for causing the one or more delta files to betransmitted. See operation 640. The delta files may, for example, betransmitted to a device, such as device 11, which, for example, containssoftware or firmware to update. According to another embodiment, thedelta files may, for example, be transmitted to another network entity,such as a server. The other network entity, according to anotherembodiment, may, for example, store the delta files and/or transmit themto a device, such as device 11. According to an example embodiment,apparatus 45 may also cause a configuration file to be transmitted alongwith the one or more delta files. As discussed above, the configurationfile may, according to one embodiment, contain the file types of each ofthe files that correspond to the one or more delta files. According toanother embodiment, the configuration file may only contain anindication of whether each file that corresponds to the one or moredelta files is a compressed file. Thus, for example, in an instant inwhich a compressed file contains multiple subfiles, the configurationfile may list each of the subfiles together with an indication that theybelong to a compressed file, such as an indication of which compressedfile they belong to.

According to an example embodiment, when an update package for updatingmultiple files is being prepared, the operations of FIG. 6 describedabove may, for example, be iteratively performed by apparatus 45 inorder to generate multiple delta files, such as one or more delta filesfor each of one or more pairs of original and modified files. Accordingto another example embodiment, apparatus 45 may first iterativelyperform steps 600 and 610, then iteratively perform steps 611 and/or 620and 630. That is, apparatus 45 may first determine whether each file isa compressed file, such as by determining a type for each file, recordthe results in a configuration file, and then generate delta filesaccording to operation 611 or operations 620 and 630 for each of thefiles based on whether they are compressed or not. Apparatus 45 mayperform operation 640, i.e., causing the delta files to be transmitted,either after they have all been generated, e.g., all at once, or as theyare generated.

Thus, according to an example embodiment, apparatus 45 associated withnetwork entity 13 may carry out operations 600, 610, 620, and 630 togenerate an update package for updating a filesystem comprising one ormore original files as follows. Apparatus 45 may first detect whethereach file to be updated in the filesystem is a compressed file, such as,for example, by detecting the type of every file in the filesystem to beupdated. The original and modified filesystems may, for example, bestored as flashfiles (images). Apparatus 45 may then cause eachcompressed modified and original file in the filesystem to bedecompressed, and, according to one example embodiment, may cause anysubfiles the compressed modified and original files contain to be storedin respective temporary folders. Next, apparatus 45 may cause one ormore delta files to be generated for each pair of decompressed originaland modified files and stored in an update package. For example,apparatus 45 may compare every file in the original filesystem to everycorresponding file in the modified filesystem, such as by, for example,causing the decompressed original and modified filesystems to be mountedby a delta calculation tool which performs the comparison. Thus,according to an example embodiment, complete files that are included inthe modified filesystem, but not the original file system, may beincluded in the update package. Files that are included in the originalfilesystem, but not the modified filesystem may be omitted from theupdate package. Files which are in both the original and modifiedfilesystem, and are not identical, would thus have a corresponding deltafile generated for them. Apparatus 45 may also cause a configurationfile to be created and added to the update package. The configurationfile may, for example, include indications of which files in theoriginal filesystem are to be removed, which files are to be added, andwhich files are to be modified. For compressed files that are to bemodified, an indication may be included in the configuration file thatlists any subfiles together along with an indication that they belong toa particular compressed file.

Turning now to FIG. 7, the operations of apparatus 45 for installing anupdate package will now be described in more detail, including examplesof operations that may precede or follow those depicted in FIG. 5b . Inthis regard and as described below, the operations of FIG. 7 may beperformed by an apparatus 45, such as shown in FIG. 3, embodied by orotherwise associated with user device 11. In this regard, the apparatus45 may include means, such as processor 50, memory device 56, andcommunication interface 54 or the like, for receiving an update packagecomprising one or more delta files corresponding to an original file.See operation 700. According an example embodiment, the update packagemay also contain at least one configuration file, such as aconfiguration file as discussed above. The update package may, forexample, be provided to the apparatus 45 by network entity 13 vianetwork 14. Apparatus 45 may further include means, such as thosementioned above, for determining whether the original file is acompressed original file. See operation 710. According to an exampleembodiment, apparatus 45 may, for example, determine whether theoriginal file is a compressed original file based on a configurationfile contained in the update package.

Having determined whether the original file is a compressed originalfile, apparatus 45 may further include means, such as processor 50 andmemory device 56 or the like, for installing the update package. Thus,apparatus 45 may include means, such as those just mentioned, forinstalling the update package in the manner depicted in FIG. 4b anddiscussed above in an instance in which the original file is not acompressed original file. See operation 711. Apparatus 45 may alsoinclude means, such as those previously mentioned, for installing theupdate package in the manner depicted in FIG. 5b in an instance in whichthe one or more of the delta files contained in the update packagecorrespond to a compressed original file. Thus, apparatus 45 may includemeans, such as processor 50 and memory device 56 or the like, fordecompressing the compressed original file. See operation 720. Apparatus45 may further include means, such as those just mentioned, forgenerating one or more modified subfiles based on the one or more deltafiles and the decompressed original file. See operation 730. Apparatus45 may also include means, such as those mentioned above, forcompressing the one or more modified subfiles, thus creating acompressed modified file. See operation 740. Having created a compressedmodified file, apparatus 45 may further include means, such as thosediscussed above, for replacing the compressed original file with thecompressed modified file. See operation 750.

According to an example embodiment, when an update package for updatinga filesystem comprising multiple original files is being installed,operations 710, 711, 720, 730, 740, and 750 of FIG. 7 described abovemay, for example, be iteratively performed by apparatus 45 in order toupdate the multiple original files. That is, apparatus 45 may receive anupdate package comprising one or more delta files corresponding tomultiple original files and then determine whether each original file isa compressed file, such as by determining a type for each file. Havingdetermined whether each original file is a compressed file, apparatus 45may then perform either operation 711, or operations 720, 730, 740, and750, on each original file depending on whether the particular originalfile is compressed. According to another embodiment, apparatus 45 mayinstead determine whether a particular original file is compressed ornot and then carry out either operation 711, or operations 720, 730,740, and 750, based on whether the particular file is compressed,repeating this process for each original file.

Thus, according to an example embodiment, apparatus 45 associated withuser device 11 may carry out operations 710, 720, 730, 740, and 750 asfollows. Apparatus 45 may, after receiving the update package, read theconfiguration file contained therein. If an update for a compressed fileis found, apparatus 45 may decompress the compressed original file.According to one embodiment, the apparatus 45 may further cause anyresulting original subfile(s) to be stored, for example, in a temporaryfolder. Next, apparatus 45 may apply the delta file(s) listed in theconfiguration file to the uncompressed original file, e.g., originalsubfiles, thus generating one more modified subfiles. Once theuncompressed original subfile(s) have been updated successfully,apparatus 45 may cause the compressed original file to be deleted orotherwise removed from the filesystem, and cause any modified subfile(s)in the temporary folder to be compressed, thus generating a compressedmodified file. Apparatus 45 may then name the compressed modified filethe same as the compressed original file (now removed). Apparatus 45may, according to an example embodiment, use one or more deltainstallers for performing the above operations. For example, one deltainstaller may be used updating normal files and one for updatingcompressed files.

As described above, FIGS. 4 through 7 illustrate flowcharts of anapparatus 45, method, and computer program product according to exampleembodiments of the invention. It will be understood that each block ofthe flowchart, and combinations of blocks in the flowchart, may beimplemented by various means, such as hardware, firmware, processor,circuitry, and/or other devices associated with execution of softwareincluding one or more computer program instructions. For example, one ormore of the procedures described above may be embodied by computerprogram instructions. Moreover, one or more of the entities describedabove, such as delta installers, delta calculation tools and the like,may also be embodied by computer program instructions. In this regard,the computer program instructions which embody the procedures describedabove may be stored by a memory device 56 of an apparatus 45 employingan embodiment of the present invention and executed by a processor 50 ofthe apparatus 45. As will be appreciated, any such computer programinstructions may be loaded onto a computer or other programmableapparatus (e.g., hardware) to produce a machine, such that the resultingcomputer or other programmable apparatus implements the functionsspecified in the flowchart blocks. These computer program instructionsmay also be stored in a computer-readable memory that may direct acomputer or other programmable apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture the execution of whichimplements the function specified in the flowchart blocks. The computerprogram instructions may also be loaded onto a computer or otherprogrammable apparatus to cause a series of operations to be performedon the computer or other programmable apparatus to produce acomputer-implemented process such that the instructions which execute onthe computer or other programmable apparatus provide operations forimplementing the functions specified in the flowchart blocks.

Accordingly, blocks of the flowchart support combinations of means forperforming the specified functions and combinations of operations forperforming the specified functions for performing the specifiedfunctions. It will also be understood that one or more blocks of theflowchart, and combinations of blocks in the flowchart, can beimplemented by special purpose hardware-based computer systems whichperform the specified functions, or combinations of special purposehardware and computer instructions.

In some embodiments, certain ones of the operations above may bemodified or enhanced. Furthermore, in some embodiments, additionaloptional operations may be included. Modifications, additions, orenhancements to the operations above may be performed in any order andin any combination.

The method, apparatus 45 and computer program product described aboveprovide many advantages. For example the method, apparatus 45 andcomputer program products may reduce the size of binary delta files usedto update compressed files. Accordingly, the method, apparatus 45 andcomputer program product described above may reduce the data that mustbe transmitted to a user device 11 in order to update software,firmware, or the like, reducing download costs for consumers, andnetwork traffic for network operators.

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Moreover, although the foregoing descriptions and the associateddrawings describe example embodiments in the context of certain examplecombinations of elements and/or functions, it should be appreciated thatdifferent combinations of elements and/or functions may be provided byalternative embodiments without departing from the scope of the appendedclaims. In this regard, for example, different combinations of elementsand/or functions than those explicitly described above are alsocontemplated as may be set forth in some of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

That which is claimed:
 1. A method comprising: receiving, by a userdevice, an update package comprising one or more delta filescorresponding to an original file stored in a memory of the user device,and a configuration file that is different from the original file, theconfiguration file indicating that the original file is a compressedfile and further indicating a file type of the original file; causing,by a processor of the user device and in response to receiving theupdate package, the original file to be decompressed; causing, by theprocessor of the user device, generation of one or more modifiedsubfiles based on the one or more delta files, the decompressed originalfile, and the configuration file; causing, by the processor of the userdevice, generation of a compressed modified file by compressing the oneor more modified subfiles; and causing, by the processor of the userdevice, replacement of the compressed original file with the compressedmodified file in memory of the user device.
 2. The method of claim 1,further comprising determining that the original file is a compressedoriginal file; wherein causing the original file to be decompressed andcausing generation of the compressed modified file are performed basedon the determination that the original is a compressed original file. 3.The method of claim 2, wherein determining that the original file is acompressed original file comprises determining, by the processor of theuser device, that the original file is a compressed original file basedon the configuration file.
 4. The method of claim 1, wherein theconfiguration file further indicates at least one of: one or more filesin an original filesystem that are to be removed; one or more files thatare to be added to the original filesystem; one or more files in theoriginal filesystem that are to be modified; and one or more subfilesthat belong to a particular compressed file.
 5. The method of claim 1,wherein the file type of the original file indicates whether theoriginal file is at least one of a folder, a symbolic link, and a normalfile.
 6. A user device comprising at least one processor and at leastone memory storing program code instructions, the memory and programcode instructions being configured to, with the processor, cause theuser device to at least: receive an update package comprising one ormore delta files corresponding to an original file stored in the memoryand a configuration file that is different from the original file, theconfiguration file indicating that the original file is a compressedfile and further indicating a file type of the original file; inresponse to receiving the update package, decompress the original file;generate one or more modified subfiles based on the one or more deltafiles, the decompressed original file, and the configuration file;generate a compressed modified file by compressing the one or moremodified subfiles; and replace the compressed original file with thecompressed modified file in the memory of the user device.
 7. The userdevice of claim 6, wherein the memory and the program code instructionsare further configured to, with the processor, cause the user device todetermine that the original file is a compressed original file; whereinthe memory and the program code instructions are further configured to,with the processor, cause the user device to decompress the original andgenerate the compressed modified file based on the determination thatthe original file is a compressed original file.
 8. The user device ofclaim 7, wherein the memory and the program code instructions arefurther configured to, with the processor, cause the user device todetermine that the original file is a compressed original file based onthe configuration file.
 9. The user device of claim 6, wherein theconfiguration file further indicates at least one of: one or more filesin an original filesystem that are to be removed; one or more files thatare to be added to the original filesystem; one or more files in theoriginal filesystem that are to be modified; and one or more subfilesthat belong to a particular compressed file.
 10. The user device ofclaim 6, wherein the file type of the original file indicates whetherthe original file is at least one of a folder, a symbolic link, and anormal file.
 11. A computer program product comprising a non-transitorycomputer readable medium storing program code portions therein, theprogram code portions being configured to, upon execution, cause a userdevice to at least: receive an update package comprising one or moredelta files corresponding to an original file stored in a memory of theuser device and a configuration file that is different from the originalfile, the configuration file indicating that the original file is acompressed file and further indicating a file type of the original file;in response to receiving the update package, decompress the originalfile; generate one or more modified subfiles based on the one or moredelta files, the decompressed original file, and the configuration file;generate a compressed modified file by compressing the one or moremodified subfiles; and replace the compressed original file with thecompressed modified file in the memory of the user device.
 12. Thecomputer program product of claim 11, wherein the program code portionsare further configured to, upon execution, cause the user device todetermine that the original file is a compressed original file; whereinthe program code portions are further configured to, upon execution,cause the user device to decompress the original and generate thecompressed modified file based on the determination that the originalfile is a compressed original file.
 13. The computer program product ofclaim 12, wherein the program code portions are further configured to,upon execution, cause the user device to determine that the originalfile is a compressed original file based on the configuration file. 14.The computer program product of claim 11, wherein the configuration filefurther indicates at least one of: one or more files in an originalfilesystem that are to be removed; one or more files that are to beadded to the original filesystem; one or more files in the originalfilesystem that are to be modified; and one or more subfiles that belongto a particular compressed file.
 15. The computer program product ofclaim 11, wherein the file type of the original file indicates whetherthe original file is at least one of a folder, a symbolic link, and anormal file.